docs: distinguish trial, global, and daily review limits in troubleshooting - #16
Open
comlaterra wants to merge 1 commit into
Open
docs: distinguish trial, global, and daily review limits in troubleshooting#16comlaterra wants to merge 1 commit into
comlaterra wants to merge 1 commit into
Conversation
…ooting The backend now returns three distinct 429 reasons (daily rate limit, TRIAL_REVIEW_LIMIT_REACHED, MAX_REVIEW_LIMIT_REACHED). Split the single 429 troubleshooting row into three so the fix guidance matches: daily -> wait for reset, trial -> upgrade, org ceiling -> contact. Also reword the usage-counter note so it no longer frames the quota as daily-only.
![agent-optibot[bot]](https://avatars.githubusercontent.com/in/934808?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Summary
This PR updates the documentation for the optibot skill, clarifying the different types of review limits a user might encounter. It expands the error handling section to provide more specific guidance for 429 errors related to daily, trial, and organizational usage quotas.
Key Changes
- The description of the Usage counter has been generalized from "daily limit" to "applicable review limit" to account for different types of quotas.
- The error message table has been expanded to differentiate between three types of
429"limit reached" errors:- Daily review limit: For individual daily quotas.
- Trial review limit: For total reviews allowed during a trial.
- Organizational review limit: For an organization's overall review ceiling.
- Each new error type now has a specific, actionable "Fix" instruction, guiding the user on how to resolve the issue (e.g., waiting, upgrading, or contacting support).
All Relevant File Changes (click to expand)
- skills/optibot/SKILL.md
- Updated the "Usage counter" description to be more general.
- Replaced the single
Review limit reached (429)error entry with three more specific entries for daily, trial, and organizational limits, each with tailored remediation steps.
💬 Feedback & Commands
Share feedback on my comments with 👍 👎 — I'll stop raising issues you push back on. Think I missed something? Adjust my sensitivity →
5 things I can do →
#optibot review— I'll re-review your latest changes (incremental)#optibot full review— I'll re-review the entire PR from scratch#optibot fix— I'll apply my suggested fixes to your code#optibot compliance— I'll run a compliance check on your changes#optibot release notes— I'll write up release notes for your production release
💡 Tip: You can configure auto-approvals, summary depth, and when I trigger reviews in Advanced Config.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
optibot-be PR #1892 (per-org trial and global review limits) introduced two new 429 reasons on top of the existing daily rate limit. The CLI (PR #28) and MCP (PR #24) render distinct messages for each, but the skill's troubleshooting table still described 429 as only "Daily quota exhausted." This aligns the skill docs with the shipped backend contract.
Changes
Review limit reached (429)troubleshooting row into three, matching the backend's three distinct 429 outcomes:TRIAL_REVIEW_LIMIT_REACHED) → upgrade atagents.getoptimal.ai/dashboard/billing.MAX_REVIEW_LIMIT_REACHED) → contactgetoptimal.ai/contact.Notes
skills/optibot/SKILL.md; no behavior or manifest changes, no version bump.optibot review -b main): Code Looks Good, no blocking findings.